Systems and methods for cloud deployment engine for selective workload migration or federation based on workload conditions

ABSTRACT

Embodiments relate to systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions. A set of aggregate usage history data can record consumption of processor, software, or other resources subscribed to by one or more users in a or clouds. An entitlement engine can analyze the usage history data to identify a subscription margin and other trends or data reflecting short-term consumption trends. An associated deployment engine can analyze the short-term consumption trends, and generate a decision to either deploy any over-subscribed resources to a set of federated backup clouds, or to one or more new host clouds. In aspects, the decision to augment the capacity of the host cloud with either a cloud federation or a complete host cloud replacement can be based on a set of selection criteria, including the margin by which the resources are over-subscribed and/or whether the over-subscription is static, increasing or accelerating, among others.

FIELD

The invention relates generally to systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions, and more particularly, to platforms and techniques for tracking the consumption of resources by virtual machines in a cloud to determine whether to deploy workloads of one or more users to federated backup clouds or to one or more replacement clouds on a permanent basis.

BACKGROUND

The advent of cloud-based computing architectures has opened new possibilities for the rapid and scalable deployment of virtual Web stores, media outlets, social networking sites, and many other on-line sites or services. In general, a cloud-based architecture deploys a set of hosted resources such as processors, operating systems, software and other components that can be combined together to form virtual machines. A user or customer can request the instantiation of a virtual machine or set of machines from those resources from a central server or cloud management system to perform intended tasks, services, or applications. For example, a user may wish to set up and instantiate a virtual server from the cloud to create a storefront to market products or services on a temporary basis, for instance, to sell tickets to or merchandise for an upcoming sports or musical performance. The user can subscribe to the set of resources needed to build and run the set of instantiated virtual machines on a comparatively short-term basis, such as hours or days, for their intended application.

Typically, when a user utilizes a cloud, the user must track the software applications executed in the cloud and/or processes instantiated in the cloud. For example, the user must track the cloud processes to ensure that the correct cloud processes have been instantiated, that the cloud processes are functioning properly and/or efficiently, that the cloud is providing sufficient resources to the cloud processes, and so forth. Due in part to the user's requirements and overall usage of the cloud, the user may have many applications and/or processes instantiated in a cloud at any given instant, and the user's deployment of virtual machines, software, and other resources can change dynamically over time. In cases, the user may also utilize multiple independent host clouds to support the user's cloud deployment. That user may further instantiate and use multiple applications or other software or services inside or across multiple of those cloud boundaries, and those resources may be used or consumed by multiple or differing end-user groups in those different cloud networks.

In terms of the management of a set of virtual machines operated by a user in a cloud, at times the user's consumption of resources in the cloud can vary and/or spike, at different times and/or under different conditions. Since in one regard consumption spikes may entail enhanced or increased subscription costs to the user, that user may wish to consider rolling their executing workload over to federated backup clouds, or to migrate the workload to an entirely new host cloud. Existing cloud management platforms do not provide the cloud user or operator with tools to automatically analyze the suitability or desirability of performing a temporary deployment of partial workloads to backup clouds, versus the permanent migration of workloads to new cloud hosts, depending on factors such as cost, expected over-subscription margins for the user's required resources, the duration of any demand peaks, and/or other factors. If a user or administrator is forced to evaluate decisions to backup versus fully migrate on a manual basis, that user could choose to migrate to an entirely new host cloud when that scale of migration is not necessary, or could choose to supply necessary resources on a backup basis from the spot marketplace, while possibly incurring subscription fees that are great than necessary.

It may be desirable to provide systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions, in which selection criteria and/or decision logic for either choosing federated cloud backup or complete or permanent migration to new cloud hosts, based on those and other factors.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an overall cloud system architecture in which various aspects of systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions can be implemented, according to embodiments;

FIG. 2 illustrates an overall cloud system architecture in which various aspects of systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions can be implemented, in further regards;

FIG. 3 illustrates a network configuration in which systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions can be implemented, including the capture and reconciliation of short-term resource consumption margins across a set of multiple users, and potentially across multiple host clouds;

FIG. 4 illustrates an exemplary data structure in which the capture and aggregation of marginal resource consumption data for multiple users, and available excess capacity from those users can be encoded and stored, according to various aspects;

FIG. 5 illustrates the identification of various over-subscription conditions for cloud resources consumed by a set of virtual machines, according to aspects;

FIG. 6 illustrates an exemplary hardware configuration for a cloud management system and/or other hardware that can support and maintain one or more cloud-based networks, according to various embodiments;

FIG. 7 illustrates a flowchart for the analysis and processing of short-term resource consumption by a set of users in different clouds, and the reconciliation of different marginal consumption values for those users including potentially across those clouds in an aggregate or offset subscription cost, that can be used in systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions, according to various embodiments; and

FIG. 8 illustrates a flowchart for the analysis and processing of translatable time periods that can be used in systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions, according to various embodiments

DESCRIPTION

Embodiments described herein can be implemented in or supported by a cloud network architecture. As used herein, a “cloud” can comprise a collection of hardware, software, services, and/or resources that can be invoked to instantiate a virtual machine, process, or other resource for a limited or defined duration. As shown for example in FIG. 1, the collection of resources supporting a cloud 102 can at a hardware level comprise a set of resource servers 108 configured to deliver computing components needed to instantiate a virtual machine, process, service, or other resource. For example, one group of resource servers in set of resource servers 108 can host and serve an operating system, and/or components, utilities, or interfaces related to that operating system, to deliver to a virtual target, and instantiate that machine with an image of that operating system. Another group of servers in set of resource servers 108 can accept requests to host computing cycles or processor time, memory allocations, communications ports or links, and/or other resources to supply a defined level of processing power or throughput for a virtual machine. A further group of resource servers in set of resource servers 108 can host and serve applications or other software to load on an instantiation of a virtual machine, such as an email client, a browser application, a messaging application, or other applications, software, or services. Other types of resource servers can be used to support one or more clouds 102.

In embodiments, the entire set of resource servers 108 and/or other hardware or software resources used to support one or more clouds 102, along with the set of instantiated virtual machines, can be managed by a cloud management system 104. The cloud management system 104 can comprise a dedicated or centralized server and/or other software, hardware, services, and network tools that communicate via network 106, such as the Internet or other public or private network, with all servers in set of resource servers 108 to manage the cloud 102 and its operation. To instantiate a new or updated set of virtual machines, a user can transmit an instantiation request to the cloud management system 104 for the particular type of virtual machine they wish to invoke for their intended application. A user can for instance make a request to instantiate a set of virtual machines configured for email, messaging or other applications from the cloud 102. The virtual machines can be instantiated as virtual client machines, virtual appliance machines consisting of special-purpose or dedicated-task machines as understood in the art, and/or as other virtual machines or entities. The request to invoke and instantiate the desired complement of virtual machines can be received and processed by the cloud management system 104, which identifies the type of virtual machine, process, or other resource being requested in that platform's associated cloud. The cloud management system 104 can then identify the collection of hardware, software, service, and/or other resources necessary to instantiate that complement of virtual machines or other resources. In embodiments, the set of instantiated virtual machines or other resources can, for example, and as noted, comprise virtual transaction servers used to support Web storefronts, Web pages, and/or other transaction sites.

In embodiments, the user's instantiation request can specify a variety of parameters defining the operation of the set of virtual machines to be invoked. The instantiation request, for example, can specify a defined period of time for which the instantiated collection of machines, services, or processes is needed. The period of time can be, for example, an hour, a day, a month, or other interval of time. In embodiments, the user's instantiation request can specify the instantiation of a set of virtual machines or processes on a task basis, rather than for a predetermined amount or interval of time. For instance, a user could request a set of virtual provisioning servers and other resources until a target software update is completed on a population of corporate or other machines. The user's instantiation request can in further regards specify other parameters that define the configuration and operation of the set of virtual machines or other instantiated resources. For example, the request can specify a specific minimum or maximum amount of processing power or input/output (I/O) throughput that the user wishes to be available to each instance of the virtual machine or other resource. In embodiments, the requesting user can for instance specify a service level agreement (SLA) acceptable for their desired set of applications or services. Other parameters and settings can be used to instantiate and operate a set of virtual machines, software, and other resources in the host clouds. One skilled in the art will realize that the user's request can likewise include combinations of the foregoing exemplary parameters, and others. It may be noted that “user” herein can include a network-level user or subscriber to cloud-based networks, such as a corporation, government entity, educational institution, and/or other entity, including individual users and groups of users.

When the request to instantiate a set of virtual machines or other resources has been received and the necessary resources to build those machines or resources have been identified, the cloud management system 104 can communicate with one or more set of resource servers 108 to locate resources to supply the required components. Generally, the cloud management system 104 can select servers from the diverse set of resource servers 108 to assemble the various components needed to build the requested set of virtual machines, services, or other resources. It may be noted that in some embodiments, permanent storage, such as optical storage or hard disk arrays, may or may not be included or located within the set of resource servers 108 available to the cloud management system 104, since the set of instantiated virtual machines or other resources may be intended to operate on a purely transient or temporary basis. In embodiments, other hardware, software or other resources not strictly located or hosted in one or more clouds 102 can be accessed and leveraged as needed. For example, other software or services that are provided outside of one or more clouds 102 acting as hosts, and are instead hosted by third parties outside the boundaries of those clouds, can be invoked by in-cloud virtual machines or users. For further example, other non-cloud hardware and/or storage services can be utilized as an extension to the one or more clouds 102 acting as hosts or native clouds, for instance, on an on-demand, subscribed, or event-triggered basis.

With the resource requirements identified for building a network of virtual machines, the cloud management system 104 can extract and build the set of virtual machines or other resources on a dynamic, on-demand basis. For example, one set of resource servers 108 may respond to an instantiation request for a given quantity of processor cycles with an offer to deliver that computational power immediately and guaranteed for the next hour or day. A further set of resource servers 108 can offer to immediately supply communication bandwidth, for example on a guaranteed minimum or best-efforts basis, for instance over a defined window of time. In other embodiments, the set of virtual machines or other resources can be built on a batch basis, or at a particular future time. For example, a set of resource servers 108 may respond to a request for instantiation of virtual machines at a programmed time with an offer to deliver the specified quantity of processor cycles within a specific amount of time, such as the next 12 hours. Other timing and resource configurations are possible.

After interrogating and receiving resource commitments from the set of resource servers 108, the cloud management system 104 can select a group of servers in the set of resource servers 108 that match or best match the instantiation request for each component needed to build the user's requested virtual machine, service, or other resource. The cloud management system 104 for the one or more clouds 102 acting as the destination for the virtual machines can then coordinate the integration of the identified group of servers from the set of resource servers 108, to build and launch the requested set of virtual machines or other resources. The cloud management system 104 can track the identified group of servers selected from the set of resource servers 108, or other distributed resources that are dynamically or temporarily combined, to produce and manage the requested virtual machine population, services, or other cloud-based resources.

In embodiments, the cloud management system 104 can generate a resource aggregation table or other record that identifies the various selected sets of resource servers in set of resource servers 108 that will be used to supply the components of the set of instantiated virtual machines, services, or processes. The selected sets of resource servers can be identified by unique identifiers such as, for instance, Internet protocol (IP) addresses or other addresses. In aspects, different sets of servers in set of resource servers 108 can be selected to deliver different resources to different users and/or for different applications. The cloud management system 104 can register the finalized group of servers in the set resource servers 108 contributing to or otherwise supporting the set of instantiated machines, services, or processes.

The cloud management system 104 can then set up and launch the initiation process to instantiate the virtual machines, processes, services, and/or other resources to be hosted and delivered from the one or more clouds 102. The cloud management system 104 can for instance transmit an instantiation command or instruction to the registered group of servers in the set of resource servers 108. The cloud management system 104 can receive a confirmation message back from each registered server in set of resource servers 108 indicating a status or state regarding the provisioning of their respective resources. Various registered resource servers may confirm, for example, the availability of a dedicated amount of processor cycles, amounts of electronic memory, communications bandwidth, services, and/or applications or other software prepared to be served and delivered.

As shown for example in FIG. 2, after coordination of the sources and configuration of resources including the hardware layer, selected software, and/or other resources, the cloud management system 104 can then instantiate a set of virtual machines 116, and/or other appliances, services, processes, and/or entities, based on the resources supplied by servers within set of resource servers 108 registered to support the one or more clouds 102 in a multiple-cloud network 110. According to aspects, cloud management system 104 can access or interact with a virtualization module, platform, or service to instantiate and operate set of virtual machines 116, such as the kernel-based virtualization manager (KVM™) available from Red Hat, Inc. of Raleigh, N.C., or others. In embodiments, the cloud management system 104 can instantiate a given number, for example, 10, 500, 1000, 20,000, or other numbers or instances of virtual machines to populate one or more clouds 102 and be made available to users of that cloud or clouds. In aspects, users may access the one or more clouds 102 via the Internet, or other public or private networks. Each virtual machine can be assigned an instantiated machine ID that can be stored in the resource aggregation table, or other record or image of the instantiated virtual machine population. Additionally, the cloud management system 104 can store data related to the duration of the existence or operation of each operating virtual machine, as well as the collection of resources utilized by the overall set of instantiated virtual machines 116.

In embodiments, the cloud management system 104 can further store, track and manage each user's identity and associated set of rights or entitlements to software, hardware, and other resources. Each user that operates a virtual machine or service in the set of virtual machines in the cloud can have specific rights and resources assigned and made available to them, with associated access rights and security provisions. The cloud management system 104 can track and configure specific actions that each user can perform, such as the ability to provision a set of virtual machines with software applications or other resources, configure a set of virtual machines to desired specifications, submit jobs to the set of virtual machines or other host, manage other users of the set of instantiated virtual machines 116 or other resources, and/or other privileges, entitlements, or actions. The cloud management system 104 associated with the virtual machine(s) of each user can further generate records of the usage of instantiated virtual machines to permit tracking, billing, and auditing of the resources and services consumed by the user or set of users. In aspects of the present teachings, the tracking of usage activity for one or more user (including network level user and/or end-user) can be abstracted from any one cloud to which that user is registered, and made available from an external or independent usage tracking service capable of tracking software and other usage across an arbitrary collection of clouds, as described herein. In embodiments, the cloud management system 104 of an associated cloud can for example meter the usage and/or duration of the set of instantiated virtual machines 116, to generate subscription and/or billing records for a user that has launched those machines. In aspects, tracking records can in addition or instead be generated by an internal service operating within a given cloud. Other subscription, billing, entitlement and/or value arrangements are possible.

The cloud management system 104 can configure each virtual machine in set of instantiated virtual machines 116 to be made available to users via one or more networks 116, such as the Internet or other public or private networks. Those users can for instance access set of instantiated virtual machines via a browser interface, via an application server such as a Java™ server, via an application programming interface (API), and/or other interface or mechanism. Each instantiated virtual machine in set of instantiated virtual machines 116 can likewise communicate with its associated cloud management system 104 and the registered servers in set of resource servers 108 via a standard Web application programming interface (API), or via other calls, protocols, and/or interfaces. The set of instantiated virtual machines 116 can likewise communicate with each other, as well as other sites, servers, locations, and resources available via the Internet or other public or private networks, whether within a given cloud in one or more clouds 102, or between those or other clouds.

It may be noted that while a browser interface or other front-end can be used to view and operate the set of instantiated virtual machines 116 from a client or terminal, the processing, memory, communications, storage, and other hardware as well as software resources required to be combined to build the virtual machines or other resources are all hosted remotely in the one or more clouds 102. In embodiments, the set of virtual machines 116 or other services, machines, or resources may not depend in any degree on or require the user's own on-premise hardware or other resources. In embodiments, a user can therefore request and instantiate a set of virtual machines or other resources on a purely off-premise basis, for instance to build and launch a virtual storefront, messaging site, and/or any other application. Likewise, one or more clouds 102 can also be formed in whole or part from resources hosted or maintained by the users of those clouds, themselves.

Because the cloud management system 104 in one regard specifies, builds, operates and manages the set of instantiated virtual machines 116 on a logical or virtual level, the user can request and receive different sets of virtual machines and other resources on a real-time or near real-time basis, without a need to specify, install, or configure any particular hardware. The user's set of instantiated virtual machines 116, processes, services, and/or other resources can in one regard therefore be scaled up or down immediately or virtually immediately on an on-demand basis, if desired. In embodiments, the set of resource servers 108 that are accessed by the cloud management system 104 to support the set of instantiated virtual machines 116 or processes can change or be substituted, over time. The type and operating characteristics of the set of instantiated virtual machines 116 can nevertheless remain constant or virtually constant, since instances are assembled from a collection of abstracted resources that can be selected and maintained from diverse sources based on uniform specifications. Conversely, the users of the set of instantiated virtual machines 116 can also change or update the resource or operational specifications of those machines at any time. The cloud management system 104 and/or other logic can then adapt the allocated resources for that population of virtual machines or other entities, on a dynamic basis.

In terms of network management of the set of instantiate virtual machines 116 that have been successfully configured and instantiated, the one or more cloud management systems 104 associated with those machines can perform various network management tasks including security, maintenance, and metering for billing or subscription purposes. The cloud management system 104 of one or more clouds 102 can, for example, install, initiate, suspend, or terminate instances of applications or appliances on individual machines. The cloud management system 104 can similarly monitor one or more operating virtual machines to detect any virus or other rogue process on individual machines, and for instance terminate an application identified as infected, or a virtual machine detected to have entered a fault state. The cloud management system 104 can likewise manage the set of instantiated virtual machines 116 or other resources on a network-wide or other collective basis, for instance, to push the delivery a software upgrade to all active virtual machines or subsets of machines. Other network management processes can be carried out by cloud management system 104 and/or other associated logic.

In embodiments, more than one set of virtual machines can be instantiated in a given cloud at the same time, at overlapping times, and/or at successive times or intervals. The cloud management system 104 can, in such implementations, build, launch and manage multiple sets of virtual machines as part of the set of instantiated virtual machines 116 based on the same or different underlying set of resource servers 108, with populations of different virtual machines such as may be requested by the same or different users. The cloud management system 104 can institute and enforce security protocols in one or more clouds 102 hosting one or more sets of virtual machines. Each of the individual sets or subsets of virtual machines in the set of instantiated virtual machines 116 can be hosted in a respective partition or sub-cloud of the resources of the main cloud 102. The cloud management system 104 of one or more clouds 102 can for example deploy services specific to isolated or defined sub-clouds, or isolate individual workloads/processes within the cloud to a specific sub-cloud or other sub-domain or partition of the one or more clouds 102 acting as host. The subdivision of one or more clouds 102 into distinct transient sub-clouds, sub-components, or other subsets which have assured security and isolation features can assist in establishing a multiple user or multi-tenant cloud arrangement. In a multiple-user scenario, each of the multiple users can use the cloud platform as a common utility while retaining the assurance that their information is secure from other users of the same one or more clouds 102. In further embodiments, sub-clouds can nevertheless be configured to share resources, if desired.

In embodiments, and as also shown in FIG. 2, the set of instantiated virtual machines 116 generated in a first cloud in one or more clouds 102 can also interact with a set of instantiated virtual machines, services, and/or processes generated in a second, third or further cloud in one or more clouds 102, comprising a multiple-cloud network 110. The cloud management system 104 of a first cloud of one or more clouds 102 can interface with the cloud management system 104 of a second, third, or further cloud of one or more clouds 102 to coordinate those domains and operate the clouds and/or virtual machines, services, and/or processes on a combined basis. The cloud management system 104 of a given cloud on one or more clouds 102 can in aspects track and manage individual virtual machines or other resources instantiated in that cloud, as well as the set of instantiated virtual machines or other resources in other clouds.

In the foregoing and other embodiments, the user making an instantiation request or otherwise accessing or utilizing the cloud network can be a person, customer, subscriber, administrator, corporation, organization, government, and/or other entity. In embodiments, the user can be or include another virtual machine, application, service and/or process. In further embodiments, multiple users or entities can share the use of a set of virtual machines or other resources.

Aspects of the present teachings relate to platforms and techniques in which a deployment engine and/or associated logic can identify over-subscription conditions for the set of virtual machines hosted in the set of host clouds 142 and operated by one or more users in the set of users 190. In aspects, the over-subscription conditions can involve the over-consumption of one or more resources which the user may wish to alleviate by re-allocating or re-deploying the subject user's workload or portions of that workload to a federation of backup clouds to supply the resource deficiencies, or to shift or migrate the workload entirely to one or more new host clouds. In aspects, the decision to shift over-subscribed consumption to a set of federated backup clouds or to an entirely new or different host cloud or clouds can be an alternative or bifurcated one, in which one option or the other is chosen. In cases, the decision to shift over-subscribed consumption to a set of federated backup clouds or to an entirely new or different host cloud or clouds can be a joint or divided decision involving some portion of the workload being migrated to federated backup clouds with another portion being migrated to a new host cloud or clouds. In aspects in general, more severe or pronounced over-consumption conditions can militate in favor of selected an entirely new host cloud, which less-severe and/or more transient over-consumption conditions can militate in favor of moving the over-subscribed portion of the workload to a set of federated backup clouds. However, the decision to deploy the workload or its components to one or the other support solution is a flexible one and can be based on a variety of rules, thresholds, and/or decision criteria, and different users can choose to apply different criteria for making a deployment choice.

Consistent with the foregoing, in general, FIG. 3 shows an illustrative network configuration in which systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions can be implemented, according to various embodiments. In embodiments as shown, one or more users can operate a user premise 144, such as a local area network with a set of servers and client machines, and/or other machines or resources. In aspects, a set of users 190 can in addition or instead operate one or more sets of virtual machines, appliances, and/or other virtual entities (not shown) in a set of host clouds 142. In aspects, the set of users 190 can be or include a collection of sub-groups of users who are each affiliated with or a part of the same entity, such as a corporation, government entity, and/or other organization. In aspects, the corporation and/or other collective entity can establish overall subscription parameters to which its users are entitled on a collective basis. In cases, the individual teams or users may not be aware or have a mechanism by which to track overall resource consumption on a collective basis, for instance to maintain service or resource level limits.

According to aspects, systems and methods according to the present teachings can permit. In aspects, the set of host clouds 142 hosting the set of users 190 can include a set of diverse and/or otherwise unrelated cloud-based networks to which the set of users 190 can subscribe for various resources under various subscription terms, limits, criteria, service level agreements, and/or other conditions, which can be recorded or reflected in a set of subscription parameters 146. The set of subscription parameters 146 can for instance be stored in the cloud store 138 hosted or accessed by a cloud management system 104, and/or in other storage resources or locations.

In embodiments as shown, an administrator and/or other user can operate a client 154 or other interface or terminal, for instance a client located in or communicating with the user premise 144 to access the set of subscription parameters 146 and other information related to the consumption of resources in the set of host clouds 142 by the set of users 190. In aspects, the consumption of resources in the set of host clouds 142 and generation of related billing events and other subscription-related activities can be tracked and managed by an entitlement engine 140, which can be hosted in the cloud management system 104 and/or in other locations, resources, or services. According to aspects, the entitlement engine 140 can communicate with a one or more resource providers 156, such as the vendors of software such as operating systems, applications, utilities, and/or other programs, services, and/or related resources. The one or more resource providers 156 can maintain part or all of the terms, conditions, limits, criteria, stipulations, and/or other parameters of the subscription of the set of users 190 to one or more resources hosted or provisioned in the set of host clouds 142, and for instance reflected in the set of subscription parameters 146.

In aspects, each host cloud in the set of host clouds 142 can capture and store a set of local usage data 152. The set of local usage data 152 can record the consumption or use of resources in a local host cloud in the set of host clouds 142, such as the number of instances of software including operating systems and applications, processor resources, memory resources, communications resources, storage resources, and/or other elements or resources. The set of local usage data 152 can include usage data for one, some, and/or all of the set of users 190 operating virtual machines or otherwise consuming resources in each particular host cloud. The entitlement engine 140 can periodically receive the set of local usage data 152 and/or updates to that information from one or more host clouds in the set of host clouds 142. The receipt of the set of local usage data 152 or any portion of the set of local usage data 152 can be performed in aspects on a pull or demand basis, where the entitlement engine 140 and/or other logic can issue commands or instructions to one or more host clouds in the set of host clouds 142, and receive that data back from the interrogated cloud or clouds. In aspects, the set of local usage data 152 can be transmitted to the entitlement engine 140 on a push basis, for instance, on a scheduled, predetermined, event-triggered, and/or other basis initiated by one or more of the host clouds in set of host clouds 142, themselves. Other channels, schedules, and techniques for the collection of the set of local usage data 152 from any one or more of the set of host clouds 142 can be used.

After receipt of the set of local usage data 152, any portion or component of the set of local usage data 152, and/or updates to the same, the entitlement engine 140 can collect and aggregate the set of local usage data 152 from the various host clouds and organize that data in a set of aggregate usage history data 148. The set of aggregate usage history data 148 can reflect recent and/or accumulated usage consumption by the set of users 190 and/or any one user or other subset thereof in all of the set of host clouds 142, over comparatively short-term periods or intervals such as minutes, one or more hours, one day, a number of days, a week, a month or months, and/or other intervals or periods. In aspects, the entitlement engine 140 can collect the set of local usage data 152 regardless of whether each of those clouds is configured to communicate with each other or not. In aspects, the set of aggregate usage history data 148 can present to the entitlement engine 140 and/or other logic the combined resource consumption by the set of users 190 across the user premise 144 and/or all operating virtual machines or entities, on an hour-by-hour, day-by-day, and/or other relatively short-term basis.

According to aspects, the entitlement engine 140 can thereby identify comparatively short-term resource consumption by the virtual machines or other entities, sites or nodes operated by the set of users 190, and capture and track that consumption compared to the short-term limits, levels, thresholds, ceilings, or caps that may be contained in the set of subscription parameters 146 for that user. The entitlement engine 140 can therefore generate or determine a short-term consumption margin for each resource which the set of users 190 consume and/or subscribe to in each cloud in the set of host clouds 142, indicating whether over the course of an hour or other period the consumption rates or values are over the subscription limit for a given resource, under the subscription limit, or at or nearly at the subscription limit for that resource.

Both the over and under-consumption margins for each resource can be captured and calculated, from which the entitlement engine 140 can generate a set of short-term user-aggregated margins 178 representing the collective short-term consumption of that resource across the diverse host clouds in set of host clouds 142, resulting in an offset or aggregate consumption value. Deviations from short-term consumption caps, limits, service level agreements (SLAs), and/or other criteria can therefore be combined, averaged, aggregated, and/or otherwise “smoothed out” to more accurately and/or timely reflect the consumption patterns of the set of users 190, as a whole on an aggregate basis. In aspects, the resource provider 156, the cloud operators or providers of the set of host clouds 142, and/or other entities can thereby charge, bill, or otherwise adjust the subscription costs or other factors encoded in the billing record 150 sent to the set of users 190, for instance via an administrator or other users, so that their subscription obligations more closely track the actual consumption behavior demonstrated by the set of users 190. In aspects, the set of short-term user-aggregated margins 178 can for instance be used to establish short-term marginal subscription costs based on short-term deviations from any subscription consumption limits, which costs can then be combined over different time periods to further average or aggregate the deviations in resource consumption. In aspects, the detection of bursts and relaxations in resource consumption over relatively short-term periods can thereby allow both positive and negative offsets or margins in subscription costs, creating a more accurate assignment of subscription rates. In embodiments as shown, the over-consumption of one or more resources and/or related events can be reflected in a set of over-subscription conditions 226, which can include records indicating the degree by which various resources (processor, memory, storage, operating system, application, etc.) exceeds any subscription caps or levels in a given interval of time.

In implementations as shown, after detecting the set of short-term user-aggregated margins 178 for each resource of interest, the entitlement engine 140 can generate a billing record 150 reflecting that event, for purposes of notification to the user and collection of billing amounts or other responses. In aspects, the entitlement engine 140 can transmit or forward the billing record 150 to the resource provider 156, such as a software vendor, to produce and transmit to the user under agreed billing arrangements. In aspects, the entitlement engine 140 can transmit or forward the billing record 150 to one or more host clouds in set of host clouds 142, including those in which an over-limit resource usage or other event took place, to potentially transmit to the set of users 190 and/or other recipient for similar purposes. In aspects, the resource provider 156 and one or more cloud operators or cloud providers of the set of host clouds 142 can maintain agreements or arrangements for the capture and forwarding of the billing record 150, and the collection of any billing amounts or credits paid by the user. In aspects, the resource provider 156 and the host cloud providers or operators can establish arrangements to share or distribute any overage payments or other payments or credits received from users between themselves. According to aspects, the monitoring and billing capture of short or long-term over-limit resource consumption can therefore be conducted, on a marginal offset or other basis, even in instances where each host cloud in set of host clouds 142 is not aware of subscription limits contained in the set of subscription parameters 146, and/or the local usage data 152 of one or more of the set of host clouds 142 is not visible to other host clouds and/or all groups or sub-groups of users within the set of users 190, and/or to other participants in the cloud-based network.

In implementations, the cloud management system 102 and/or other server, logic, and/or resource of the set of host clouds 142 and/or other clouds or networks can be configured with a deployment engine 222, which can be or include application(s), software, logic, services, hardware, and/or other resources used to implement various processing and decisions for the support or migration of over-subscribed resources and/or workloads operated by a user. In aspects as shown, the cloud management system 102 supporting a set of host clouds 142 can host, incorporate, and/or access the deployment engine 222, and interact with or use the deployment engine 222 and/or other logic, application, and/or service to build, maintain, access, and monitor the one or more over-subscription conditions 226, and analyze those conditions to generate a decision to migrate or deploy the workload 228 and/or any portions of the workload 228 to either one or more replacement clouds 214, to a set of federated backup clouds 218, and/or to combinations of those potential hosts.

The deployment engine 222 and/or other logic, application, and/or service can access, generate, monitor, and update the one or more over-subscription conditions 226 to identify those resources whose consumption has exceeded any limits in the user's set of subscription parameters 146, and by what amount. In aspects, for example, the one or more over-subscription conditions 226 can indicate or reflect that for User A, at present or over some selected time period (e.g., the last hour or day), the consumption of processor resources has been running at a rate of 105% of the subscription limit. The one or more over-subscription conditions 226 can likewise for instance indicate or reflect that for User A, at present or over some selected time period, the consumption of memory resources has been running at a rate of 115% of the subscription limit, while the number of operating system instances has been running or averaging 220 instances against a subscription limit of 2000 instances, producing an over-subscription condition of 20 instances or 10% of the allocated limit. Other hardware, software, services, and/or other resources can be tracked in the one or more over-subscription conditions 226, which can likewise store similar information for more than one user.

In implementations as shown, after the various resource consumption rates, levels, and/or other subscription-related information is gathered in the one or more over-subscription conditions 226, the deployment engine 222 and/or other application, logic, and/or service can analyze that data using a set of selection criteria 220 to determine whether to alleviate the over-consumption of resources by deploying the user's workload 228 and/or the over-subscribed resources and/or other portions thereof to the set of federated backup clouds 218, to the one or more replacement clouds 214, to combinations thereof, and/or to other cloud support networks In aspects, the set of selection criteria 220 can comprise a variety of functions, thresholds, limits, variables, calculations, and/or other criteria that can be used to identify a preferred, acceptable, optimal, and/or other choice for the deployment of the workload 228 operating under the one or more over-subscription conditions 226. In aspects, it may be noted that the workload 228 for a user can reflect the sum total of all executing processes including software, data access, virtual machine configuration, operation, and support, and/or other associated tasks executing in the set of host clouds 142. In aspects, the set of selection criteria 220 can be automatically generated by the deployment engine 222 and/or other application, logic, and/or service can be or include criteria inputted or supplied by the user. In cases, the set of selection criteria 220 can reflect a single or simple decision variable or criteria, such as “select the support option providing the minimum necessary resources to supply the workload (228) including any over-subscribed resources at minimum cost,” given the degree of over-subscription reflected in the one or more over-subscription conditions 226. In cases such as the noted example where the user is experiencing over-consumption rates of 5%, 15%, and 10% of processor, memory, and operating system over-consumption, the deployment engine 222 and/or other application, logic, and/or service can determine that those represent relatively limited over-subscription conditions, and allocate the over-subscribed portion of the workload 228 to the set of federated backup clouds 218, based on a lowest-cost determination for using or “rolling over” those backup clouds on a comparatively temporary basis. In aspects, if the over-subscription conditions are projected to differ or vary over different time periods, the deployment engine 222 and/or other application, logic, and/or service can in addition or instead of selecting just one set of federated backup clouds 218, can also selected multiple sets or layers of federated backup clouds, at different times and/or based on other conditions.

On the other hand, in cases, where the user is experiencing relatively high over-subscription margins or thresholds such as 150% of processor limits, 225% of memory limits, and 300% of operating system instances, the deployment engine 222 and/or other application, logic, and/or service may generate a determination that the migration of the entire workload 228 of the user to one or more replacement clouds 214 may represent the preferred or optimal choice. In cases, that may be the case because the net subscription cost of moving and hosting the user's workload 228 in the one or more replacement clouds 214 may be less than continuing to attempt to acquire the necessary resources from the set of federated backup clouds 218 on a market basis, and/or because those federated support networks may not be able to provide resources at the required levels or at the required times. Other combinations of criteria and/or decision logic can be incorporated in the set of selection criteria 220.

In terms of data capture of the usage, subscription, billing and related information used to detect and record resource consumption, excess resource capacity flows, and/or other information and/or other events, FIG. 4 illustrates an aggregate usage history record 180 that can be used to store the set of aggregate usage history data 148 which can store and encode various data, attributes, criteria, and/or other information used to track and manage the differential or marginal resource consumption in the set of host clouds 142 and/or other host sites by the set of users 190. In aspects, the aggregate usage history record 180 can be encoded as a relational or other database, table, tree, file, object, and/or other data store or data structure. In aspects as shown, the set of aggregate usage history data 148 encoded and stored in the aggregate usage history record 180 can include tables, entries, values, attributes, and/or other information including set of short-term consumption data 162 reflecting the usage of one or more resources in the set of host clouds 142 by each user in the set of users 190 over one or more short-term consumption periods 160. In aspects, the one or more short-term consumption periods 160 can be or include a variety of periods or intervals, such as one-hour intervals (as shown), but can also be or include other periods or intervals, such as 1, 5, 10, 15, and/or 30 minutes, 2 hours, 8 hours, 12 hours, one day or 24 hours, 3 days, one week, and/or other time intervals or periods. In aspects, the one or more short-term consumption periods 160 can reflect a period or interval (or periods or intervals) that is/are shorter than the period called for in the set of subscription parameters 146 as the basic or defined interval in terms of resource consumption limits or levels, service level agreements (SLAs), and/or other subscription criteria or settings. In aspects, the short-term subscription period 160 can be defined to be equal to the subscription period(s) or interval(s) defined by the set of subscription parameters 146. In aspects, the value, length, or short-term nature of the one or more short-term consumption periods 160 can be configured as dynamic, flexible, or configurable units, rather than defined as a strict number of minutes, hours, days, and/or weeks or other units. In aspects, the short-term subscription period 160 can be set or configured by a user, such as the cloud provider(s) or cloud operator(s) of the set of host clouds 142, by the one or more resource providers 156, by the set of users 190 whose set of aggregate usage history data 148 is being track and administered, and/or by other users or entities. In aspects, a record can be kept in the aggregate usage history record 180 recording, for each cloud in the set of host clouds 142 in which the set of users 190 subscribes and/or uses or consumes resources, the short-term consumption data 162 indicating an amount, rate, or other metric of resource consumption over each of the one or more short-term consumption periods 160.

In aspects as shown, the aggregate usage history record 180 can likewise include, for each cloud in the set of host clouds 142 and each resource consumed or used in that cloud, the short-term consumption limit 164 for that user based on the set of subscription parameters 146 and/or other information for each user in the set of users 190. In aspects, the entitlement engine 140 and/or other logic can generate and store a short-term subscription margin 166 reflecting the deviation in terms of under-consumption or over-consumption of each resource for which each user in the set of users 190 has a short-term subscription limit 164. The short-term subscription margin 166 can thereby reflect, on a comparatively short-term basis, such as every 15 or 30 minutes, hour, 8 hour, one-day or other period, the marginal amount by which the consumption of a subscribed resource by the set of users 190 is fluctuating and possibly deviating from the short-term consumption limit 166. In aspects, the short-term subscription margin 166 can reflect a negative value, indicating that a lesser amount of one or more resource is being consumed or has been consumed compared to limits or levels in the set of subscription parameters 146. In aspects, the short-term subscription margin 166 can reflect a positive value, indicating that a greater amount of one or more resource is being consumed or has been consumed compared to limits or levels in the set of subscription parameters 146.

In aspects, the entitlement engine 140 and/or other logic can similarly collect and sum or aggregate the short-term subscription margin 166 over each host cloud in the set of host clouds 142 in which the set of users 190 is using or consuming the subject resource to generate a set of short-term user-aggregated margins 178, representing the comparatively short-term or immediate net consumption of the resource over the set of users 190. In aspects, the set of short-term user-aggregated margins 178 can also be aggregated over two or more clouds of the set of host clouds 142. The set of short-term user-aggregated margins 178 can be calculated and stored for each hour and/or other period represented by the one or more short-term consumption periods 160, for instance over the course of one hour, day, one week, one month, and/or other period or interval. In aspects as shown, the entitlement engine 140 and/or other logic or service can further calculate and store an aggregate consumption total 172 over a defined period, such as a one-day or other period, summing or aggregating the set of short-term user-aggregated margins 178 for a resource for one user over that period. In aspects, the aggregate consumption total 172 can thereby encode the combined, net, averaged, and/or otherwise aggregated effect of the various under and over-limit consumption events by the set of users 190 in the set of host clouds 142 over 12 hours, 24 hours, and/or other predetermined interval. The entitlement engine 140 and/or other logic can, in addition, also calculate and store a set of offset subscription costs 170 reflecting the costs, surcharges, credits, and/or other adjustments for each hour and/or other period in the one or more short-term consumption periods 160 for a particular resource across the set of users 190. A resource provider, cloud operator, and/or other entity may be entitled, for instance, to an overage subscription fee or charge at a rate of $0.50 per instance for operating system (OS) instances over the short-term consumption limit 164 based on that usage, and/or other adjustments or factors. In aspects, the set of offset subscription costs 170 can be computed at a fixed rate, and/or at a dynamically adjusted rate, for instance based on time of usage, total resource consumption, and/or other parameters. The entitlement engine 140 and/or other service or logic can also generate an aggregate offset subscription cost 174 which combines or sums the set of offset subscription costs 170 for each of the one or more short-term consumption periods 160 for a predetermined period, such as one day, one week, one month, and/or other period or interval, across the set of users 190. The aggregate offset subscription cost 174, and other consumption variables and cost factors, can in aspects thereby more accurately correspond to the overall rate or absolute amount of resource consumption in the set of host clouds 142 by the set of users 190. In embodiments, the entitlement engine 140 and/or other logic can in addition combine, sum, and/or otherwise aggregate or net the aggregate offset subscription cost 174 for multiple individual resources whose consumption data in turn has been aggregated across multiple host clouds in the corresponding aggregate offset subscription cost 174, to generate a total offset subscription cost 182. In aspects, the total offset subscription cost 182 can encapsulate the net marginal resource usage by the set of users 190 against all short-term consumption limits 164 with associated costs or credits across all host clouds in the set of host clouds 142, all subscribed resources, and/or all daily or other operative time periods constructed from the one or more short-term consumption periods 160.

In aspects and as likewise shown in FIG. 4, the entitlement engine 140 and/or other logic or service can also capture, identify, and/or record the one or more over-subscription conditions 226 reflected in the set of aggregate usage history data 148 for one or more users. In aspects, the one or more over-subscription conditions 226 can be derived from the set of short-term consumption margins 166, short-term consumption data 162, and/or other data or variables related to the user's virtual machine operation and resource consumption in the set of host clouds 142.

According to those and related aspects of the present teachings, and as for example further shown in FIG. 5, the deployment engine 222, entitlement engine 140, and/or other logic, application, and/or service can operate to generate, manipulate, analyze, and update the one or more over-subscription conditions 226, including time-series of resource consumption by the user's virtual machines, as shown. In aspects, the deployment engine 222 and/or other application, logic, and/or service can generally monitor the resource consumption flows of a user to identify the one or more over-subscription conditions 226 by tracking the consumption of resources which exceed one or more terms in the user's set of subscription parameters 146. It may be noted, the one or more over-subscription conditions 226 can likewise second-order or higher-level details about the user's resource consumption trends, such as whether the rate at which resources are being consumed above limit is decreasing, staying the same, or increasing. In cases, the deployment engine 222 and/or other application, logic, and/or service can track the rate of change or “acceleration” of one or more over-subscription conditions, to determine those trends which may represent a particularly vigorous change in consumption patterns. In such cases or others, the set of selection criteria 220 can be biased or weighted in favor of selecting one or more replacement clouds 214 to support the over-subscribed resources, since the user's consumption of those resources may be viewed to be likely to continue to expand. Other trends, characteristics, data points, and/or calculations can be used to generate the one or more over-subscription conditions 226 and/or related information.

FIG. 6 illustrates an exemplary diagram of hardware and other resources that can be incorporated in a cloud management system 104 configured to communicate with the set of instantiated virtual machines 116, entitlement engine 140, user premise 144, client 154, set of host clouds 142, and/or other entities, services, or resources via one or more networks 106 and/or other connections, according to embodiments. In embodiments as shown, the cloud management system 104 can comprise a processor 130 communicating with memory 132, such as electronic random access memory, operating under control of or in conjunction with an operating system 136. The operating system 136 can be, for example, a distribution of the Linux™ operating system, the Unix™ operating system, or other open-source or proprietary operating system or platform. The processor 130 also communicates with a cloud store 138, such as a database stored on a local hard drive, and a management engine 128, to execute control logic and control the operation of virtual machines and other resources in one or more clouds 102, the set of host clouds 142, and/or other collections of clouds. The processor 130 further communicates with a network interface 134, such as an Ethernet or wireless data connection, which in turn communicates with the one or more networks 106, such as the Internet or other public or private networks. The processor 130 and/or the cloud management system 104 can likewise communicate with the entitlement engine 140, the deployment engine 222, the set of subscription parameters 146, the set of usage history data 148, the user premise 144, the client 154, the set of host clouds 142, and/or other interfaces, applications, machines, sites, services, data, and/or logic. Other configurations of the cloud management system 104, associated network connections, and other hardware, software, and service resources are possible. It may be noted that in embodiments, the client 154 and/or other hardware machines, platforms, or engines can comprise the same or similar resources as cloud management system 104, or can be configured with different hardware and software resources.

FIG. 7 illustrates a flowchart of overall processing to perform the tracking of resource consumption, management of subscription parameters, short-term billing capture and margin reconciliation and related activities, according to various embodiments of the present teachings. In 702, processing can begin. In 704, an administrator or other user can initiate and/or access the set of aggregate usage history data 148 for the set of users 190 and/or other user or users via the entitlement engine 140 and/or other logic. In 706, an administrator or other user can initiate and/or access the set of subscription parameters 146, indicating, for instance, resource consumption rates, limits, caps, and/or other subscription parameters or factors by which the set of users 190 can subscribe to resources of the set of host clouds 140. In 708, the entitlement engine 140 and/or other logic can track, register, and/or monitor the set of aggregate usage history data 148 to determine the short-term subscription margin 166 for each resource to which the set of users 190 subscribes, in each host cloud in set of host clouds 142 to which the user is registered. In aspects, the short-term subscription margin 166 can be tracked or monitored for each period in the one or more short-term consumption periods 160. In aspects, the one or more short-term subscription periods 160 can be or include one or more periods such as, for instance, one-hour periods as shown, and/or can also or instead include other periods such as periods or intervals of 1, 5, 10, 15, or 30 minutes, 8-hour periods, 12-hour periods, 24-hour periods, and/or other periods or intervals. In aspects, the one or more short-term consumption periods 160 can correspond to the short time periods tracked by the cloud management system, the entitlement engine 140, the set of host clouds 142, and/or other cloud logic or infrastructure. In aspects, the one or more short-term consumption periods 160 can comprise equally-spaced intervals, and/or can include intervals of different durations or lengths.

In 710, the entitlement engine 140 and/or other logic can sum the short-term subscription margin 166 across all users in the set of users 190 and/or all host clouds for each period of the one or more short-term consumption periods 160 to generate the short-term user-aggregated subscription margin 172 for that respective period. For instance, in exemplary records as shown in FIG. 4, the number of operating system (OS) instances instantiated and/or run by the set of users 190 in a given hour across the set of host clouds 142 can be totaled, so that instances of under-limit consumption offset instances of over-limit consumption, resulting in a net short-term cloud-aggregated subscription margin 178 for the one or more short-term consumption periods 160 across all users in set of users 190 for one or more all host clouds. In cases, the set of short-term user-aggregated margins 178 may reflect a net over-consumption (positive) value for that hour or other period (as illustratively shown), or can reflect an under-consumption (negative) value for that same period. A zero margin (at-limit) value can also be reflected.

In 712, the entitlement engine 140 and/or other logic can generate the set of marginal consumption totals 168 reflecting the total combined short-term subscription margin 166 for each resource being tracked over a 24-hour, or other interval or period. For example, and as shown for instance in FIG. 4, the under-limit (e.g. recorded as a negative value) and over-limit (e.g. recorded as a positive value) margins or increments of consumption under or over the short-term consumption limit 164 for each one or more short-term consumption periods 160 can be summed or combined to determine the set of short-term user-aggregated margins 178 for each respective resource over a 24-hour period, again for one or more host clouds. In aspects, other periods or intervals other than a 24-hour period can be used to sum the values reflected in the set of short-term user-aggregated margins 178. The values reflected in the set of short-term user-aggregated margins 178 can thereby reflect the netting out of the under-consumption and over-consumption values for a given resource in two or more dimensions, namely over multiple users and/or two or more host clouds, and over multiple instances of the one or more short-term consumption periods 160, averaging out consumption fluctuations by the set of users 190 in relation to the set of short-term consumption limits 164.

In 714, the entitlement engine 140 and/or other logic can generate the set of offset subscription costs 170 for each of the one or more short-term consumption periods 160 corresponding to the set of short-term user-aggregated margins 178 for each subscribed resource. For instance, if the record for a given one or more short-term consumption periods 160 reflects the over-consumption of 20 operating system instances, the assigned overage cost of that usage may be, for instance, $0.50 times 20 instances, or $10.00 for that hour or other period. In 716, the entitlement engine 140 and/or other logic can generate the aggregate offset subscription cost 174 for one 24-hour or other period, representing the combination of the set of offset subscription costs 170 over a multiple number of the one or more short-term consumption periods 160, such as the combination of 24 one-hour periods, or other intervals, periods, or multiples. In 718, the entitlement engine 140 and/or other logic can generate the billing record 150 based on the aggregate offset subscription cost 174 for each resource being tracked and/or metered for the set of users 190, and/or based on other costs, adjustments, offsets, and/or factors. In 720, the entitlement engine 140 and/or other logic, entities, or resources, such as the operator of the set of host clouds 142, can transmit the billing record 150 to an administrator for the set of users 190 and/or other user or other recipient. In 724, as understood by persons skilled in the art, processing can repeat, return to a prior processing point, jump to a further processing point, or end.

FIG. 8 illustrates various processing that can be used in systems and methods for a cloud deployment engine for selective workload migration or federation based on workload conditions, according to aspects of the teachings. In 802, processing can begin. In 804, an administrator and/or other user can initiate the deployment engine 222 and/or other logic, applications, services, or tools to manage the workload distribution and/or resource consumption for one or more users of a set of virtual machines, such as virtual machines hosted in or instantiated on one or more cloud-based networks, and/or hosted in or instantiated on one or more premise networks. In 806, the deployment engine 222 and/or other application, logic, and/or service can access and/or read or extract the set of aggregate usage history data 148 for the subject user or users, as well as the set of subscription parameters 146 for the user(s) of the set of virtual machines 116, which again can for instance be or include individual users and/or collections of users, such as a corporation and/or other entity. In 808, the deployment engine 222 and/or other application, logic, and/or service can analyze the set of aggregate usage history data 148 and/or other information to detect and/or identify one or more over-subscription conditions 226 that may exist in the user's or users' workload 228. The deployment engine 222 and/or other application, logic, and/or service can determine, for instance, that the user's workload 228 is presently, currently, and/or otherwise immediately or in real-time consuming 110% of the subscribed processor resources, 105% of the subscribed memory resources, and 15 instances more of an operating system than available under the user's set of subscription parameters 146.

In 810, the deployment engine 222 and/or other application, logic, and/or service can analyze the potential migration or deployment of the over-subscribed portion of the workload 228 to the one or more replacement clouds 214, to generate a projected cloud replacement outcome and/or other prediction or report. In aspects, the projected federated outcome can indicate expected deployment results such as, merely for example, “workload (228) can be migrate to replacement cloud A on a permanent basis at a subscription cost of $125 per day at the over-subscribed rate of resource consumption,” and/or other projections or outcomes. In 812, the deployment engine 222 and/or other application, logic, and/or service can analyze the potential migration or deployment of the over-subscribed portion of the workload 228 to the set of federated backed up clouds 218, to generate a projected federated outcome and/or other prediction or report. In aspects, the projected federated outcome can indicate expected deployment results such as, merely for example, “over-subscribed resources can be supplied by cloud federation B for a period of 12 hours at a temporary subscription cost of $25 per hour,” and/or other projections or outcomes.

In 814, the deployment engine 222 and/or other application, logic, and/or service can apply the set of selection criteria 220 and/or other factors to the projected federated outcome and the projected cloud replacement outcome, as appropriate. For instance, the set of selection criteria 220 can indicate that the preferred or selected hosting target will be that hosting alternative which provides at least a set of resources sufficient to support or cover 15% the highest over-subscription rate of resource consumption, while incurring no more than 10% greater subscription cost than that of the same resources (including over-subscription) hosted in the original host cloud 210. Other factors, parameters, variables, thresholds, tests, and/or criteria can be contained in the set of selection criteria 220, which criteria can in cases be multiple or compound in nature.

In 816, the deployment engine 222 and/or other application, logic, and/or service can select and/or identify the set of federated backup clouds 218 and/or the one or more replacement clouds 214 for migration or deployment activity, based on the set of selection criteria 220, the projected cloud replacement outcome, the projected federation outcome, user input(s) or selection(s), and/or other factors, tests, thresholds, and/or criteria, as appropriate. In 818, the deployment engine 222 and/or other application, logic, and/or service can initiate the migration of the workload 228 and/or the over-subscribed portion of the workload 228 to the set of federated backup clouds 218 and/or the one or more replacement clouds 214, as appropriate. In 820, the deployment engine 222 and/or other application, logic, and/or service can meter, bill, and/or otherwise administer the migrated workload 228 and/or any portions thereof that is temporarily hosted in the set of federated backup clouds 218 and/or the one or more replacement clouds 214.

In 822, the deployment engine 222 and/or other application, logic, and/or service can initiate the migration of the workload 228 and/or the over-subscribed portion of the workload 228 from the set of federated backup clouds 218 and/or the one or more replacement clouds 214 to the original host cloud 210 after the over-subscription conditions have ended or subsided, as appropriate. While in embodiments the workload 228 can be returned to the original host cloud 210, in embodiments, the workload 228 and/or portions thereof can likewise be migrated or transported to new, additional, or other host clouds, as desired. In 824, processing can jump to a prior processing point, proceed to a further processing point, repeat, or end.

The foregoing description is illustrative, and variations in configuration and implementation may occur to persons skilled in the art. For example, while embodiments have been described in which the cloud management system 104 for a particular cloud resides in a single server or platform, in embodiments the cloud management system 104 and associated logic can be distributed among multiple servers, services, or systems. Similarly, while embodiments have been described in which one group of servers within a set of resource servers 108 can provide one component to build a requested set of virtual machines, in embodiments, one group of resource servers can deliver multiple components to populate the requested set of instantiated virtual machines 116, and/or other machines, entities, services, or resources. For further example, while embodiments have been described in which a user connects to or accesses the entitlement engine 140 via one client 154, in embodiments, multiple clients, portals, services, and/or other access points to the entitlement engine 140 can be used. Likewise, while embodiments have been described in which one entitlement engine 140 and/or deployment engine 222 operate to manage the resource consumption, billing, and/or other activities of one or more users in a set of host clouds 142, in embodiments, multiple deployment engines, scheduling engines, and/or other logic or services can perform the same or similar logic to manage deployment options. Other resources described as singular or integrated can in embodiments be plural or distributed, and resources described, as multiple or distributed can in embodiments be combined. The scope of the invention is accordingly intended to be limited only by the following claims. 

1. A method of distributing cloud workloads, comprising: accessing a set of usage history data for a set of resources consumed by a set of virtual machines executing a workload; determining one or more over-subscription conditions based on the usage history of the set of virtual machines; generating a projected cloud replacement outcome based on a potential migration of the workload to at least one replacement cloud; generating a projected cloud federation outcome based on a potential migration of the over-subscribed portion of the workload to at least one set of federated backup clouds; and selecting at least one of the at least one replacement cloud and the at least one set of federated backup clouds for migration of at least the over-subscribed portion of the workload based on at least a set of selection criteria, the projected cloud replacement outcome, and the projected cloud federation outcome.
 2. The method of claim 1, wherein at least one of the projected cloud replacement outcome or the projected cloud federation outcome comprises a subscription cost for hosting of the at least over-subscribed portion of the workload.
 3. The method of claim 1, wherein the selecting is based on a rate of resource consumption increase of the at least over-subscribed portion of the workload.
 4. The method of claim 3, wherein the selecting comprises selecting the at least one replacement cloud when the rate of resource consumption increase exceeds a threshold set in the set of selection criteria.
 5. The method of claim 1, wherein the set of selection criteria comprises an upper over-subscription limit for at least one of the resources consumed by the set of virtual machines.
 6. The method of claim 5, wherein the selecting comprises selecting the set of federated backup clouds when the consumption of the at least one resource in the over-subscribed portion of the workload does not exceed the upper over-subscription limit.
 7. The method of claim 5, wherein the selecting comprises selecting the at least one replacement cloud when the consumption of the at least one resource in the over-subscribed portion of the workload exceeds the upper over-subscription limit.
 8. The method of claim 1, wherein the at least one set of federated backup clouds comprises a plurality of sets of federated backup clouds configured in layers based on time periods estimated in the projected cloud federation outcome.
 9. The method of claim 1, wherein the set of selection criteria comprises at least one of available processor capacity, available memory capacity, available storage capacity, available operating system instances, available application instances, or a time period for which the over-subscribed portion of the workload can be hosted.
 10. The method of claim 1, further comprising terminating the at least over-subscribed portion of the workload in the at least one replacement cloud or the set of federated backup clouds when the set of usage history data indicates the one or more over-subscription conditions have ended.
 11. A system for distributing cloud workloads, comprising: an interface to data store storing a set of usage history data for a set of virtual machines consuming a set of resources executing a workload; and a processor, communicating with the data store via the interface and being configured to— determine one or more over-subscription conditions based on the usage history of the set of virtual machines, generate a projected cloud replacement outcome based on a potential migration of the workload to at least one replacement cloud, generate a projected cloud federation outcome based on a potential migration of the over-subscribed portion of the workload to at least one set of federated backup clouds, and select at least one of the at least one replacement cloud and the at least one set of federated backup clouds for migration of at least the over-subscribed portion of the workload based on at least a set of selection criteria, the projected cloud replacement outcome, and the projected cloud federation outcome.
 12. The system of claim 11, wherein at least one of the projected cloud replacement outcome or the projected cloud federation outcome comprises a subscription cost for hosting of the at least over-subscribed portion of the workload.
 13. The system of claim 11, wherein the selecting is based on a rate of resource consumption increase of the at least over-subscribed portion of the workload.
 14. The system of claim 13, wherein the selecting comprises selecting the at least one replacement cloud when the rate of resource consumption increase exceeds a threshold set in the set of selection criteria.
 15. The system of claim 11, wherein the set of selection criteria comprises an upper over-subscription limit for at least one of the resources consumed by the set of virtual machines.
 16. The system of claim 15, wherein the selecting comprises selecting the set of federated backup clouds when the consumption of the at least one resource in the over-subscribed portion of the workload does not exceed the upper over-subscription limit.
 17. The system of claim 15, wherein the selecting comprises selecting the at least one replacement cloud when the consumption of the at least one resource in the over-subscribed portion of the workload exceeds the upper over-subscription limit.
 18. The system of claim 11, wherein the at least one set of federated backup clouds comprises a plurality of sets of federated backup clouds configured in layers based on time periods estimated in the projected cloud federation outcome.
 19. The system of claim 11, wherein the set of selection criteria comprises at least one of available processor capacity, available memory capacity, available storage capacity, available operating system instances, available application instances, or a time period for which the over-subscribed portion of the workload can be hosted.
 20. The system of claim 11, further comprising terminating the at least over-subscribed portion of the workload in the at least one replacement cloud or the set of federated backup clouds when the set of usage history data indicates the one or more over-subscription conditions have ended. 